5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

DISPLAY


The DISPLAY statement converts the contents of the field associated with the specified item(s) from internal to external format and displays them to the user.

  ?????  DISPLAY  ??? ?????????????????????? ??? (AT APPEARANCE # ???)
  (1)             (2) (3)                    (4)                  (5)

(1) T/F execution conditions
(2) Application ID
(3) Field name or predefined field
(4) Occurrence (constant/index)
(5) Appearance (constant/index)

Using the Statement

The appearance number can be used if the same field appears more than once on an image. If the application ID, field name, occurrence number, and appearance number are not specified (left blank), the DISPLAY statement affects all of the items painted on the associated image.

DISPLAY is one of the characteristic-type statements. Refer to the common attributes of all the statements in this category in the Characteristic-Type Statements section of this manual.

The operation of a DISPLAY statement affects only the next generation of an image. In other words, the item characteristics are reset each time an image is produced,

Restrictions

Note that, because the DISPLAY statement operates on items rather than fields, this statement is meaningful only in event points that are associated with an image.

Statement Ignored

The system ignores any DISPLAY statements specified in non-image-related event points.

Related Statements

BLANK, BLINK, BOLD, BRIGHT, COLOR, DIM, FONT, INVERSE, NO BOLD, NO ULINE, NORMAL, PICTURE, ULINE

Example

The DISPLAY statement is used to cause the current contents of a field to appear on the image. In this example, the customer's credit status displays as BAD if the customer's balance exceeds the credit limit. If it does not, OK displays. 

        IF       TAR CUSTOMER BALANCE                     GT TAR CUSTOMER CREDIT LIMIT
  T     SET      TAR CUSTOMER CREDIT STATUS               =      BAD
  F     SET      TAR CUSTOMER CREDIT STATUS               =      OK
        DISPLAY  TAR CUSTOMER CREDIT STATUS               (AT APPEARANCE #)

Application Design Manual                                         "Powered by Appx Software"

640

©2006 By APPX Software, Inc. All Rights Reserved